Sequential function chart (sfc) online editing without reset

ABSTRACT

A change monitor as part of an online editor of a sequential function chart (SFC) programming environment monitors edits to a control routine. The change monitor provides warning to users before taking actions that would result in a reset of the control routine currently being executed by an industrial controller. The change manager reduces or eliminates many situations that would otherwise result in a reset as well by instructing online editor as to what language elements need to be assembled to implement the change. The change monitor also filters the manner in which reset warnings are given to reduce unnecessary distractions.

TECHNICAL FIELD

The subject invention relates to industrial control systems and, moreparticularly, to systems and methods that perform online editing ofcontroller routines.

BACKGROUND OF THE INVENTION

Industrial controllers are special purpose processing devices used forcontrolling (e.g., automated and semi-automated) industrial processes,machines, manufacturing equipment, plants, and the like. A typicalcontroller executes a control program or routine in order to measure oneor more process variables or inputs representative of the status of acontrolled process and/or effectuate outputs associated with control ofthe process. Such inputs and outputs can be binary, (e.g., “1” or “0,”“on” or “off,” . . . ), and/or analog, assuming a continuous range ofvalues. A typical control routine can be created in a controllerconfiguration environment that has various tools and interfaces wherebya developer can construct and implement a control strategy usingindustrial and conventional programming languages or graphicalrepresentations of control functionality. Such control routine can bedownloaded from the configuration system into one or more controllersfor implementation of the control strategy in controlling a process ormachine.

Measured inputs received from a controlled process and outputstransmitted to the process can pass through one or more input/output(I/O) modules in a control system. Such modules can serve in thecapacity of an electrical interface between the controller and thecontrolled process and can be located local or remote from thecontroller. Inputs and outputs can be recorded in an I/O memory. Theinput values can be asynchronously or synchronously read from thecontrolled process by one or more input modules and output values can bewritten directly to memory by a processor for subsequent communicationto the process by specialized communications circuitry. An output modulecan interface directly with a controlled process by providing an outputfrom memory to an actuator such as a motor, drive, valve, solenoid, andthe like.

During execution of the control routine, values of the inputs andoutputs exchanged with the controlled process can pass through memory.The values of inputs in memory can be asynchronously or synchronouslyupdated from the controlled process by dedicated and/or common scanningcircuitry. Such scanning circuitry can communicate with input and/oroutput modules over a bus on a backplane or network. The scanningcircuitry can also asynchronously or synchronously write values of theoutputs in memory to the controlled process. The output values from thememory can be communicated to one or more output modules for interfacingwith the process. Thus, a controller processor can simply access thememory rather than needing to communicate directly with the controlledprocess.

Several types of programming languages are used to create a controlroutine. A third part of open international standard IEC 61131 relatesto programming languages and defines two graphical and two textual PLCprogramming language standards: Ladder diagram (LD); Function blockdiagram (FBD); Structured text (ST); Instruction list (IL); andSequential function chart (SFC). Offline and online editing ofrespective control routines in each of these languages except forinstruction list are often facilitated by third party programmingsoftware.

The ability to make, test, and implement edits online providesadvantages for expeditiously performing maintenance, responding to aparticular situation of an on-going industrial process, or otherproblems. This is particularly true for function block diagram (FBD) andstructured text (ST) programming languages since these types of controlroutines complete an execution cycle with each controller scan. Thus, anoriginal routine may be readily replaced with an edited routine withoutdisturbing an on-going industrial process.

By contrast, sequential function chart (SFC) programming languageusually does not complete an execution cycle during one scan of anindustrial controller. A SFC is similar to a flowchart in that itnavigates through steps and transitions to perform specific operationsdefined by actions and typically is used for high-level management ofmultiple operations, repetitive sequences of operations, batchprocesses, motion control using structured text, and state machineoperations. Online editing of an SFC control routine results inresetting to an initial step of the routine, which can result in seriousinterruptions to the process.

As an example, consider a beer brewing industrial process that employsan SFC control routine with the following steps in the brewing recipe:(1) Add the ingredients; (2) Mix and heat ingredients; (3) Pour intocooling container; (4) Cool batch; (5) Pour into a fermenting container;(6) Ferment batch; and (7) Bottle beer. Each one of these steps in therecipe can take anywhere from a few hours to days or weeks. In asituation where the brew master starts a batch of beer and proceedsthrough steps 1 and 2, but upon step 3 a valve malfunctions the beercould undesirably be left in a heated container too long. The brewmaster can attempt to save the batch by changing the manner in which itis cooled, but that might require modifying the Sequential FunctionChart routine code. Unfortunately, altering the Sequential FunctionChart routine code to make these changes can cause the process torestart at the initial step, which is to add the ingredients. This resetof the process is undesirable since it means that the chart and themachine would be out of synchronization. The only way to rectify thiswould be by dumping the current batch and starting the process over atstep 1. Alternatively, a customer could write custom code to implementsuch change. However, such changes typically intuitiveness of the SFCand online editing tool, and thus are often prone to introducing errors.In addition, such changes may require a level of expertise that isunavailable or otherwise expensive to obtain.

SUMMARY OF THE INVENTION

The following presents a simplified summary of the invention in order toprovide a basic understanding of some aspects of the invention. Thissummary is not an extensive overview of the invention. It is intendedneither to identify key or critical elements of the invention nor todelineate the scope of the invention. Its sole purpose is to presentsome concepts of the invention in a simplified form as a prelude to themore detailed description that is presented later.

Change monitoring of online editing of a routine reduces the need forresetting the routine of a controller in order to implement the change.Thereby, a currently operating step of the routine may proceed withoutinterruption. In particular, monitoring pending changes affords anopportunity for notifications to a user so that unnecessary resets maybe avoided. Moreover, tracking of the specific changes affordsopportunities for committing changes of only those language elementsnecessary to implement the change. Thereby, downloading an entireroutine that would force a reset is avoided.

In one aspect, a user employs an online editor via a user interface tomake pending edits of a language element of an online routine. Thepending edits are held in a language container or copy. A change monitorresponds to a pending edit by identifying whether any changes, includingadditions, modifications, and/or deletions, between an original languageelement and the pending edit are of a nature to necessitate a reset. Thechange monitor can then perform a measure to prevent a reset of thecontroller.

In another aspect, a method includes classifying attributes of languageelements that when changed and committed to form a routine would requireresetting of a routine of a controller. Then pending edits to an onlineroutine are monitored so that a measure can be performed to preventreset when those classified attributes are detected.

To the accomplishment of the foregoing and related ends, the invention,then, comprises the features hereinafter fully described. The followingdescription and the annexed drawings set forth in detail certainillustrative aspects of the invention. However, these aspects areindicative of but a few of the various ways in which the principles ofthe invention can be employed. Other aspects, advantages and novelfeatures of the invention will become apparent from the followingdetailed description of the invention when considered in conjunctionwith the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a high-level diagram of an online programming system.

FIG. 2 is a high-level diagram of an online programming systemincorporating a machine learning component.

FIG. 3 is high-level flow diagram of a methodology performed by theon-line programming system of FIG. 1.

FIG. 4 illustrates a block diagram of an online programming environmentof a sequential function chart (SFC) routine executed by a controller tooperate an on-going industrial control process.

FIG. 5 illustrates a flow diagram of a main methodology performed by theindustrial control process of FIG. 3.

FIG. 6 illustrates a flow diagram of an On Element Verify methodologyperformed by a change monitor of the online programming environment ofFIG. 3.

FIG. 7 illustrates a flow diagram of an On Element Delete methodologyperformed by the change monitor of the online programming environment ofFIG. 3.

FIG. 8 illustrates a reset warning filter methodology performed by thechange monitor of the online programming environment of FIG. 3.

FIG. 9 illustrates a depiction of a graphical user interface of theonline programming environment of FIG. 3.

FIG. 10 illustrates an exemplary networking environment, wherein thenovel aspects of the claimed subject matter can be employed.

FIG. 11 illustrates an exemplary operating environment that can beemployed in accordance with the claimed subject matter.

DETAILED DESCRIPTION OF THE INVENTION

A change monitor as part of an online editor of a sequential functionchart (SFC) programming environment that monitors edits to a controlroutine. The change monitor provides a warning to users before takingactions that would result in a reset of an industrial controllercurrently executing an original routine. The change monitor reduces oreliminates many situations that would otherwise result in a reset aswell by instructing an execution module as to what language elementsneed to be assembled to implement the change. The change monitor alsofilters the manner in which reset warnings are given to reduceunnecessary distractions.

The present invention is described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the present invention. It may be evident, however, thatthe present invention may be practiced without these specific details.In other instances, well-known structures and devices are shown in blockdiagram form in order to facilitate describing the present invention.

As utilized in this application, terms “component,” “system,”“controller,” “device,” “manager,” and variants thereof are intended torefer to a computer-related entity, either hardware, a combination ofhardware and software, software, or software in execution. For example,a component may be, but is not limited to being, a process running on aprocessor, a processor, an object, an executable, a thread of execution,a program, and/or a computer. By way of illustration, both anapplication running on a server and the server can be a component. Oneor more components can reside within a process and/or thread ofexecution and a component can be localized on one computer and/ordistributed between two or more computers.

With reference to FIG. 1, a programmable industrial process 10 isoperated by a controller 11 that performs a routine 12 composed oflanguage elements that is subject to a reset component 13. Changes to acertain attribute 14 of the routine 12 necessitate a reset of theroutine 12, which can be disruptive to the programmable industrialprocess 10 for routines 12 intended to execute over an extended periodof time before returning to an initial state. Changes to anotherattribute 14 of the routine 12 may not require a reset, however. Aprogramming system 15 can communicate via a data link 16 to thecontroller 11 so that an online editor 17 can makes changes to thelanguage elements that would affect attributes 14 of the routine 12. Inparticular, the online editor 17 creates pending edits 18 that include achanged attribute 19 as compared to the attributes 14 of the routine 12.Substituting the pending edits 18 for the routine 12 as is generallyunderstood would cause the reset component 13 to reset the changedversion of routine 12. In order to avoid or minimize resets duringonline editing, a change monitor 20 of the programming system 15assesses the changed attributes 19 of the pending edits 18 and performsa reset averting action 21 in response.

It should be appreciated with the benefit of the present disclosure thatan attribute of the routine can comprise a quality, a characteristic, astep, a value, a structural sequence, etc. A change can include an addedattribute, a modified attribute and/or a deleted attribute. For clarity,the controller 11 operating one routine 12 can be reset to commitchanged attributes to begin executing. In an illustrative aspect,however, the controller 11 can perform a plurality of routines,functions, processes, operations, etc., (not shown) such that theroutine 12 alone is reset without interrupting other routines.

In FIG. 2, an alternative a programmable industrial process 30 isoperated by a controller 31 that performs a routine 32 composed oflanguage elements that is subject to a reset component 33. Changes to acertain attribute 34 of the routine 32 necessitate a reset of theroutine 32, which can be disruptive to the programmable industrialprocess 30 for a routines 32 intended to execute over an extended periodof time before returning to an initial state. Changes to anotherattribute 34 of the routine 32 may not require a reset, however. Aprogramming system 35 can communicate via a data link 36 to thecontroller 31 so that an online editor 37 can makes changes to thelanguage elements that would affect attributes 34 of the routine 32. Inparticular, the online editor 37 creates pending edits 38 that include achanged attribute 39 as compared to the attributes 34 of the routine 32.Substituting the pending edits 38 for the routine 32 as is generallyunderstood would cause the reset component 33 to reset the changedversion of routine 32. In order to avoid or minimize resets duringonline editing, a change monitor 40 of the programming system 35assesses the changed attributes 39 of the pending edits 38 and performsa reset averting action 41 in response. In some instances, the resetaverting action 41 is a warning that allows a user to make changes in away that avoids a reset or allows the user to knowingly commit thechanges that will cause a reset, especially in situations whereresetting is not detrimental. In other instances, the reset avertingaction 41 is the change tracking capability that allows for committingthe changes in a way that a reset is not necessary.

The change monitor 40 includes a machine learning component 42,comprised of a rule-based logic component 43 and an artificialintelligence (AI) component 44, that is more adept at recognizingchanged attributes 39 that require or do not require a reset and/orselects a more appropriate reset averting action 41 among severaloptions.

The rules-based logic component 43 can be employed to automate certainfunctions described or suggested herein. In accordance with thisalternate aspect, an implementation scheme (e.g., rule) can be appliedto define types of attributes that should be acted upon or ignored,correlate language elements to attributes, create rules that are awareof a certain state of the routine 32 and whether or not the pending edit38 pertains to the current state, preferences of a user interacting withthe online editor 37 for types of reset averting actions, etc. By way ofexample, it will be appreciated that the rule-based implementation canautomatically define criteria for a user level of expertise orauthorization level to affect the industrial process 30. In responsethereto, the rule-based implementation can change the amount ofnotifications given, the level of detail provided, and/or prevent editsaltogether that would result in a reset.

The AI component 44 can facilitate automating performance of one or morefeatures described herein such as predicting user inclinations. Thus,employing various AI-based schemes can assist in carrying out variousaspects thereof. For example, a process for determining whether or not aparticular online edit detrimentally affects an ongoing industrialprocess 30 to be facilitated via an automatic classifier system andprocess. For instance, the AI component 44 could be trained in alearning mode wherein the process 30 has actuated components deactivatedor simulated. A user could indicate what changes in operation should notoccur without warning a user. Then the AI could detect what classes ofchanges result in changes to these operations or not, learning whatonline edits are of concern and what online edits can be ignored.

A classifier is a function that maps an input attribute vector, x=(x1,x2, x3, x4, xn), to a class label class(x). A classifier can also outputa confidence that the input belongs to a class, that is,f(x)=confidence(class(x)). Such classification can employ aprobabilistic and/or statistical-based analysis (e.g., factoring intothe analysis utilities and costs) to prognose or infer an action that auser desires to be automatically performed.

A support vector machine (SVM) is an example of a classifier that can beemployed. The SVM operates by finding a hypersurface in the space ofpossible inputs that splits in an optimal way the triggering inputevents from the non-triggering events. Other classification approaches,including Naïve Bayes, Bayesian networks, decision trees, neuralnetworks, fuzzy logic models, maximum entropy models, etc., can beemployed. Classification as used herein also is inclusive of statisticalregression that is utilized to develop models of priority.

As will be readily appreciated from the subject specification, thesubject invention can employ classifiers that are pre-trained (e.g., viaa generic training data from multiple users) as well as methods ofreinforcement learning (e.g., via observing user behavior, observingtrends, receiving extrinsic information). Thus, the subject inventioncan be used to automatically learn and perform a number of functions,including but not limited to determining, according to a predeterminedcriteria, what constitutes a reset condition of concern, when/if tocommunicate impending controller reset, when/if to prevent a controllerreset, preferences for types of data to exchange, etc.

In FIG. 3, a methodology 50 for change monitoring of online editing of acontroller routine begins in block 52 by classifying types of attributechanges of a routine that necessitate reset of a controller toimplement. When an online editing session commences, pending edits aremonitored in order to reduce the likelihood of an unnecessary orinadvertent reset that would detrimentally affect an ongoing controlledprocess. In particular, in block 56 when an attribute change isdetected, a determination is made in block 58 as to whether thisdetected change is classified as causing a reset. If not, in block 60implementation is limited to making changes necessary to the routine andavoiding unnecessary changes that would cause a reset. By managing theextent of the changes, it becomes unnecessary to reset the routine inall or most instances of changes when unable to determine whether or notthe reset is required. If in block 60 the change is classified aswarranting a reset, then a warning is given to the user in block 62 thata reset will occur if the change is implemented. Then the user canchoose to knowingly proceed or to create an alternate change that couldavoid a reset. Thus, the methodology 50 performs a reset averting actionfor both an instance where a change requires a reset and an instancewhere a change does not.

FIG. 4 illustrates an industrial control system 100 having a controllerprogramming environment 102 that performs online edits of an SFC routine104 composed of programming language components that is executed by anindustrial controller 106 to control an industrial process 108. Aworkstation A 110 performs the online edit by forming a networkconnection via a communication module 112 to the controller 106 over adata bus 114. Original language elements 116 contained within a coderepository or library 118 are accessed so that a copy in an originalcontainer 120 may be readily accessed by the workstation A 1110. A userinteracts via an input 122 and output 124 of a graphical user interface(GUI) 126 with a routine editor 130 that creates pending edits based onthe original routine 120 in a pending container 132. The user can acceptthe pending edits that are then stored in a test container 134.

A change monitor 140 responds to the changes as they occur in thepending edits 132, comparing them against a reset list 142, which onlythe change monitor 140 has access to, to determine which changes wouldresult in a reset, warning the user via the GUI 126, and perhaps one ormore workstations B 144 also on the data bus 114. Given that the changemonitor 140 tracks the extent of the changes as well as whether a resetis necessary, the change monitor further instructs an execution model150 as to what language components 104 should be changed in thecontroller 106. The change model 150 is an aspect of the routine editor130 that handles the transfer of software components (e.g., languageelements) to commit a pending change for execution. The change trackingand reset implication tracking made by the change monitor 140 enablesthese transfers to be done in a way that avoids reset of the routine 104in many instances.

If the change monitor 140 determines that the SFC does not need to bereset, based on the changes the user made, just the test edit attributesof elements that did change are downloaded to the controller 106 and thecurrently executing Step will continue to execute. Firmware supportswrapping changed pieces of the SFC in a transaction. If any part of thedownload fails, the entire process will fail and not be allowed. Thiswill prevent incomplete data from being executed in the controller 106in case of communication loss, etc. The execution model 150 need onlydownload attributes of an element which has changed in the pending editscontainer 132. To accomplish this, the execution model 150 queries thechange monitor 140, which in turn responds with what the execution model150 is to download.

The change monitor 140 also filters reset warnings received from the oneor more other workstations 144 so that unnecessary distractions arereduced on the GUI 126.

Table 1A is an illustrative list of the types of online edits that wouldcause a reset but for the intervention of the change monitor 140. Notethat currently only two changes would not cause a reset with the benefitof the change monitor, specifically change language element descriptionand change text box contents.

TABLE 1A Online Action Move Language Elements (no wiring changes) CreateText Box Delete Text Box Step Preset Use Expression On/Off Step PresetExpression Change Step Limit High Use Expression On/Off Step Limit HighUse Expression Step Limit Low Use Expression On/Off Step Limit Low UseExpression Step Show Action in Routine Step Never Display Description inRoutine Step Save Element Defaults Step Property Page value changesAction Body Action Preset Use Expression On/Off Action Preset UseExpression Action Property Page value changes Transition ConditionTransition Never Display Description in Routine

In other instances, while the change monitor 140 may not be in aposition to avoid a reset due to a change, the change monitor 140 doesprovide alerts to the user so that such resets are done knowingly andthus hopefully without detrimental effects to an on-going industrialprocess. An illustrative example of the types of changes that result insuch notifications are given in Table 1B:

TABLE 1B Online Action Create Step Create Action Create TransitionCreate Stop Create Branch Create Branch Leg Create SBR/RET Create WireDelete Step Delete Action Delete Transition Delete Stop Delete BranchDelete Branch Leg Delete SBR/RET Delete Wire Change Step SpecifierInitial Step Step Enable Alarm Step Change Action Order Step InsertElement Defaults Step Insert Factory Defaults Change Action SpecifierChange Action Order Action Qualifier Action Boolean Action Indicator TagChange Transition Specifier Diverge Branch Change Sequence Order SBR/RETAdd parameter SBR/RET Delete parameter SBR/RET Move parameters

It should be appreciated with the benefit of the present disclosure thatthis listing is illustrative. In some applications, particular attributechanges listed in Table 1B need not force a reset. For clarity, theseclassifying decisions are depicted as sorting such types of attributechanges. However, the change monitor 140 can further evaluate eachattribute change on a case by case basis to evaluate the effect on aparticular portion of the routine 104, finding that such a change (e.g.,addition, modification or deletion) actually need not force a reset whencommitted.

Elements in routine 104 are inserted and maintained in the reset list142 as a speed optimization. Having an easy way to lookup and retrievean element prevents the change monitor 140 from having to search throughthe elements in each container 120, 132, 134 every time one is neededfor comparison. For example, the reset list 142 can track an element IDwith full specifier with a corresponding original element ID, pendingelement ID, test element ID, and whether a reset is required for thisrecord.

The reset list 142 is a list of all language elements in the SFC routine104. Conceptually, the reset list 142 can be thought of as a table likeTable 2 (see above), but can be stored in the Hash Table of the changemonitor 140. Each row corresponds to a language element in itsrespective language container. Each column represents a piece of data,such as depicted in Table 2, about the element, which is containedwithin a newly created structure and includes the element name string;original, pending, and test edit unit identifier (UID) for the elementin each container; and a Boolean that indicates whether or not thechanges to the element between containers will necessitate a reset.

TABLE 2 Data Type Description Element Name String Contains the Element'sname. Original UID DWORD Contains the UID of the Element with the givenelementName in the Original Container. Pending UID DWORD[ ] Contains theUID(s) of the Element(s) with the given elementName (multiple Elementsmay have this elementName) in the Pending Edits Container. Test UIDDWORD The UID of the Element in the Test Container with the givenelementName. Reset Required bool Indicates if the change to the Elementrequires a reset to occur or not.

The language elements of a SFC include steps, stops, branches,transitions, and actions. A step represents a major function of theprocess and contains the actions that occur at a particular time, phaseor station. A transition is a true or false condition that tells the SFCwhen to go to the next step. A simultaneous branch executes more thanone step at a time, thus SFC programming language supports simultaneousoperations. A selection branch chooses between different executionpaths. Text boxes may be added to assist in support and maintenance ofthe routine. It is also possible to insert structured text actionsinside an SFC program (e.g., this is the standard way to work on integervariables).

While the illustrative programming language described here is asequential function chart (SFC), it is to be appreciated with thebenefit of the present disclosure that such routines can be generated inessentially any programming language. Examples of suitable languagesinclude industrial control languages (e.g., structured text (ST),sequential function chart (SFC), functional block diagram (FBD),instruction list (IL), and ladder diagram (LD)), C, C++, C#, GraphicalMotion Language (GML), Java, Flow-Charts, etc., and/or any combinationthereof. Such flexibility allows a developer to select a language(s)suited to a particular task(s) and provides for decomposition intological elements and modularization to construct instruction sets thatcan be re-used, mitigate errors, and increase programming and userefficiency. Aspects described herein can be applied to these variousprogramming languages.

In FIG. 5, a methodology 190 for operating an industrial process with anSFC control routine begins after the routine has been downloaded to thecontroller in block 195 and execution has commenced from the initialstep in block 200. In block 202, execution has proceeded beyond theinitial step. When a determination is made in block 204 that a change isneeded to the routine, an online editor is invoked in block 206 in orderto start a pending edit from with the routine. Then a change is made inblock 208.

Online edits in sequential function chart programming are defined as anychange made while online with the controller, such as changing addingand deleting language elements, editing transitions between languageelements, changing the size and shape of a text box, etc. All of thisinformation is stored in the controller to allow the sequential functionchart program to be reconstructed upon upload.

Each sequential function chart routine in the online edit state can havethree views in the illustrative version. The Original View is an optionthat is available when there are pending edits and/or test edits for aroutine, and the user elects to view the original version of theroutine. Clicking on this view displays the original (i.e., no edits)routine image from the controller (i.e., before you made any edits) in aread-only mode. It should be appreciated that the term “view” refers toa copy that is displayed to a user via a graphical user interface andthat a “library container” or “copy” refers to a data structurecontaining SFC and any edits from which the view is generated.

The Original View is on the controller when online. The Pending EditsView is created when edits are made to a copy of the original routinestored in the workstation database. These edits are not committed untilaccepted by the user. The pending edits view represents theworkstation's local image of the routine edits, and is visible only tothe person performing those edits.

The Test Edits View is created after accepting a pending edit when thecontroller is in Run mode. This view is stored in the controller as wellas in the offline workstation, and can therefore be viewed by allworkstations. The test edits view always represents the test routineimage in the controller. The Test Edits view is read-only.

Without the benefit of the change monitor 140, note that due to itsstate-based execution architecture, when switching from executing theOriginal SFC to the Test Edits version, and vice versa, the SFC isautomatically reset to the initial step and all stored actions are reset(i.e., no longer running). When switching between the Test and Untestonline edit state, control is being switched between the Test Editsversion and the Original version. Note that when switching control fromthe Original version to the Test Edits version, the values of any SFCelements in the Test Edits version will initially be in the same statethey were left in by the logic in the Original version. Addinginitialization logic where appropriate can allow elements to startcontrolling the industrial process correctly when activated by testingand untesting edits. When parameter values are changed in an SFCelement, the values are being changed in all versions of the routine.For example, changing a parameter value in the Test Edits version alsochanges the value of that parameter in the Original version, even if theOriginal View is the version of the routine actually running in thecontroller.

However, with the benefit of the change monitor, after a change is madein block 208, the new change is compared with the downloaded routine inblock 210. If the change requires a reset in block 212, then a warningis presented to the user, depicted as a displaying a popup warning inblock 214. If not requiring a reset in block 212 or after displaying thewarning in block 214, then a determination is made in block 216 as towhether changes are complete. If not, processing returns to block 208for more edits. If complete, then the user initiates acceptance of thechanges in block 218. A further determination is then made as to whetherthe overall changes are of a nature requiring a reset in block 220. Ifso, a new chart is downloaded to the controller in block 222 and analert of the reset is sent to all connected users in block 224.Returning to execution in block 202 thus causes the reset. If theoverall changes do not require a reset in block 220, however, then justparts of the chart that have changed are downloaded to the controller inblock 226 and the industrial process is maintained at the current stepin block 228, followed continued execution at block 202. The changemonitor thus detects changes between an Original Language Container andany Pending or Test Containers spawned from it. For any change that ismade, the change monitor is notified, which in response detects if thechange will cause a reset to occur and increments a “reset counter” ifit does. The SFC change monitor allows the user to undo the changeaction and decrements the reset counter accordingly. If the reset countis non-zero, a reset will occur. If the reset count is zero, the SFCchange monitor organizes and sends the pieces of the chart that didchange as a full reset is not required.

In addition, the change monitor 140 performs internal cleanup after a“Cancel Pending Edits” occurs to maintain state and direct othersubsystems how to do their cleanup of the cancelled edits. The changemonitor 140 directs subsystems how to assemble the newly made edits inthe controller when the user elects to “Accept Pending Edits” since thechange monitor 140 track the information necessary to make thatdecision. “Assembling” within the present context specifically meansthat the test edits in the controller replace the original edits in thecontroller, ending the online edits process. The change monitor 140performs internal state-management after the user accepts test editssince to track changes made to a routine.

In the exemplary version of the change monitor 140, the determination ofwhether a change warrants a reset is determined by one of twoverification methods that process the change along with the languageelement that was modified, which is then passed from the change monitor140 to the execution model 150. In FIG. 6, the first method, an OnElement Verify methodology 300, deals with creating, modifying andundeleting elements and connections. The On element Verify methodology300 is called anytime that a verification takes place, handlingsituations such as when a user undoes a delete, changes a specifier, orchanges the scope of a tag. In block 302, a determination is made as towhether the element in question is verified, and exits in block 304 ifnot. If verified, then the element name string is obtained in block 306for correlating with the reset list.

Then a determination is made in block 308 as to whether the element is aLeg, which is indicated by the element name string being empty. If so,in block 310, the branch to which the leg is connected is obtained andacted upon as if the branch had been passed to the method since thechange monitor is not concerned with legs. After blocks 308 and 310,then a further determination is made as to whether the element namestring can be located in the reset list in block 312. If the elementname string cannot be found, then the element is newly created in thepending container and is added to the reset list in block 314, marked ascausing a reset in block 316, and exits in block 304.

If in the reset list in block 312, then the element from the pendingedit source container is obtained via its UID in the reset list in block318. Then, the attributes for the stored (base) element is compared bythe change monitor with the (current) element for testing for reset. Theattributes compared are focused on the subset that would determinewhether or not a reset is required if changed. In the illustrativeversion, the attributes compared depend upon what type of element isbeing compared. If the element is a step or a stop, the latter being aspecial step, then an attribute comparison is made as to whether this(1) is initial step, and (2) what the next transition is. If the elementis an Action, then the comparison of attributes is made regarding (1)what is the next action, (2) what is the parent step, (3) what is theaction qualifier, and (4) is the action Boolean. If the element is atransition, the comparison is made as to what is the next element. Withregard to elements that are a branch, all branch types are evaluated bycomparing element name strings between the passed in branch and the basebranch. The branches do not need to be concerned with the number of legsconnected to them as steps and transitions always check to see what theyare connected to, and will therefore automatically check the number oflegs on a branch for the branch. If the branch is a diverge-selectbranch, the change monitor compares the leg sequence priority of thebranch and the base branch. If they are different, a reset is required,otherwise no reset is required.

After the specific comparison in block 320, a determination is made inblock 322 as to whether any differences were detected that warrant areset. If so, the element is marked as causing a reset in block 316 andthe method exits in block 304. If not, then the element is marked as notcausing a reset in block 324 and the method exits in block 304.

In FIG. 7, the second method, an On Element Delete method 350 deals withthe deletion of an element or when a user undoes a create. Noverification is done on that element since it no longer exists and adelete has the potential to cause a reset to occur. In bock 352, adetermination is made as to whether the element is a textbox, sincechanges to a textbox should not cause a reset. Thus, if a textbox, themethod 350 exits in block 354. If not a textbox in block 352, then theelement name string is obtained in block 356. If the element is thendetermined to be a leg in block 358, then the element name string isobtained in block 360 for the branch that the leg is connected to sincethe change monitor is not concerned with the legs specifically. If not aleg in block 358, then in block 362 the element name string is obtainedand searched for in the reset list. If not in the reset list, then theelement never was in the list and the method fails.

After block 360 or 362, then a determination is made as to whether thereis a UID for the element in its source container in block 364. If so,then in block 366 the UID for the element is deleted from the pendingedits container. In block 368, the Boolean flag indicating that a resetis required is set to “false” as this element was added during pendingedits and is now removed. If not in the source container in block 364,then a determination is made in block 370 as to whether a UID for theelement is in the test or original views. If so, those entries willmarked as not causing a reset in block 372, else the entire entry isremoved from the reset list in block 374, and the method exits in block354.

If the reset list contains one or more elements that require a reset, anew chart will be downloaded and a reset will occur. If the reset listhas zero elements requiring a reset, a comparison of all elements in alanguage container will be done and only the elements that changed willneed to be downloaded and a reset will not occur when the pending editsare accepted. Since the user is warned of any required reset prior toaccepting pending edits, the user has an opportunity to manually changethe state to one that will not cause a reset. Note that physicallymoving elements, adding/deleting/modifying text boxes,adding/deleting/modifying descriptions, or any other change that willonly affect the depiction reconstruction data does not cause a reset tooccur. After the pending edits are accepted, the change monitor movespending edits UID holders to the UID holder in the target container. Thepending edit UID list is emptied.

In FIG. 8, with the increase of reset warnings that may be produced bythe user's workstation and by other workstations that are incommunication, a methodology 400 for filtering reset warnings is addedby listening for changes to the base routine in block 402. If a changeis received in block 404, then a determination is made as to whether thechange is from another workstation in block 406. If so, a determinationis made as to whether the change is one that would warrant a reset inblock 408. If not, then in block 410 any GUI notification (e.g., popupwindow) is hidden if it would otherwise be visible to the user. If thenotification pertains to a reset, then the popup or other GUInotification is presented in block 412. After block 410 or 412, themethod continues to listen in block 402 for another change.

If in block 406 the change was from the user's workstation rather thanfrom another workstation, then a determination is made as to whether thechange warrants a reset in block 414. If not, then the popup is hiddenif visible on the user's workstation in block 416. Otherwise, the resetwarning is presented, such as by displaying a popup on the user'sworkstation in block 418. After block 416 or 418, then the methodcontinues to listen for more changes in block 402. The functionality ofthe My workstation popup in block 418 provides greater interaction, suchas the ability to navigate to the depiction of the change.

In FIG. 9, an exemplary GUI window 600 allows selecting a container toview an original, a pending edits or a test version of an SFC routine602 in a view pane 604. An online view watermark 606 visually indicateswhether this is original version (e.g., a document symbol), a pendingedits as depicted (e.g., document symbol with an overlaid pencil), or atest version (e.g., document symbol with overlaid lightning bolt). Theaddition of a reset warning symbology, depicted as a curved arrow at608, indicates that the present SFC chart includes changes that warranta reset. Specifically, the pending edits will have the modifiedannotated watermark whenever at least one change exists that will causea reset. The test edits view will have the annotated watermark wheneverthere is at least one change that exists in the test edits containerthat will cause a reset and the controller is in untest mode. Theoriginal container will have the annotated watermark when the test editscontainer has at least one change will cause a reset and the controlleris in test mode. The reasoning for this is that the container will causea reset when switched, but the container that is currently executingcannot cause a reset. Reset icon 610 is displayed when any routine has areset condition in any container as well, including pending and/or test.

There will be additional annotations to a pending edits container userinterface when a reset is required. A reset icon 610 is displayed in astatus bar tray 612. Passing a cursor 614 over the reset icon 610 causesa tooltip message 616 that provides additional information, such as thedepicted “One or more SFC routines will be reset to their initial stepalong with all stored actions being reset.” the tool tip message 616 isspecific to the active SFC routine if that routine requires a reset. Ifthe active SFC routine does not require a reset, the message is the sameas if there is a reset in the controller elsewhere and there is noactive routine. The status bar reset icon 610 can be selected (e.g.,doubled clicked) to open up the routine requiring a reset in a resetelement browser. If the active SFC routine requires a reset, then thisview will be brought to the top. If no routine

Dialog boxes, such as an untest program edits dialog box or the depictedtest edits dialog box 620, include a listing 622 of routines in aviewing pane 624 with a reset icon 626 next to those routines thatrequire a reset. Clicking the reset icon 626 opens a reset elementbrowser (not depicted) with the routine being viewed highlighted.Additional warnings can be added to the dialog box for additionalexplanation such as “The reset icon indicates that the SFC routine willbe reset to their initial step along with their stored action beingreset.”

It should be appreciated that finalizing edits via the GUI window 600enables a user to select a single button instead of manually having tohit an accept pending edits button, followed by a test edits button,followed by an accept test edits button. When the user finalizes theiredits, the change monitor 140 goes through the steps implicit infollowing these interim steps, however.

In addition, a popup message 630 can be presented on the window 600,such as the depicted one stating that “accepting these edits will causeMySFC to reset to its initial step along with all stored actions beingreset.”

FIG. 10 is a schematic block diagram of a sample-computing environment1000 with which the claimed subject matter can interact. The system 1000includes one or more client(s) 1010. The client(s) 1010 can be hardwareand/or software (e.g., threads, processes, computing devices). Thesystem 1000 also includes one or more server(s) 1020. The server(s) 1020can be hardware and/or software (e.g., threads, processes, computingdevices). The servers 1020 can house threads to perform transformationsby employing the subject innovation, for example.

One possible communication between a client 1010 and a server 1020 canbe in the form of a data packet adapted to be transmitted between two ormore computer processes. The system 1000 includes a communicationframework 1040 that can be employed to facilitate communications betweenthe client(s) 1010 and the server(s) 1020. The client(s) 1010 areoperably connected to one or more client data store(s) 1050 that can beemployed to store information local to the client(s) 1010. Similarly,the server(s) 1020 are operably connected to one or more server datastore(s) 1030 that can be employed to store information local to theservers 1020.

With reference to FIG. 11, an exemplary environment 1100 forimplementing various aspects of the claimed subject matter includes acomputer 1112. The computer 1112 includes a processing unit 1114, asystem memory 1116, and a system bus 1118. The system bus 1118 couplessystem components including, but not limited to, the system memory 1116to the processing unit 1114. The processing unit 1114 can be any ofvarious available processors. Dual microprocessors and othermultiprocessor architectures also can be employed as the processing unit1114.

The system bus 1118 can be any of several types of bus structure(s)including the memory bus or memory controller, a peripheral bus orexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, Industrial StandardArchitecture (ISA), Micro-Channel Architecture (MSA), Extended ISA(EISA), Intelligent Drive Electronics (IDE), VESA Local Bus (VLB),Peripheral Component Interconnect (PCI), Card Bus, Universal Serial Bus(USB), Advanced Graphics Port (AGP), Personal Computer Memory CardInternational Association bus (PCMCIA), Firewire (IEEE 1394), and SmallComputer Systems Interface (SCSI).

The system memory 1116 includes volatile memory 1120 and nonvolatilememory 1122. The basic input/output system (BIOS), containing the basicroutines to transfer information between elements within the computer1112, such as during start-up, is stored in nonvolatile memory 1122. Byway of illustration, and not limitation, nonvolatile memory 1122 caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable programmable ROM(EEPROM), or flash memory. Volatile memory 1120 includes random accessmemory (RAM), which acts as external cache memory. By way ofillustration and not limitation, RAM is available in many forms such asstatic RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), doubledata rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM(SLDRAM), Rambus direct RAM (RDRAM), direct Rambus dynamic RAM (DRDRAM),and Rambus dynamic RAM (RDRAM).

Computer 1112 also includes removable/non-removable,volatile/non-volatile computer storage media. FIG. 11 illustrates, forexample a disk storage 11124. Disk storage 1124 includes, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, Jaz drive, Zip drive, LS-100 drive, flash memory card, or memorystick. In addition, disk storage 1124 can include storage mediaseparately or in combination with other storage media including, but notlimited to, an optical disk drive such as a compact disk ROM device(CD-ROM), CD recordable drive (CD-R Drive), CD rewritable drive (CD-RWDrive) or a digital versatile disk ROM drive (DVD-ROM). To facilitateconnection of the disk storage devices 1124 to the system bus 1118, aremovable or non-removable interface is typically used such as interface1126.

It is to be appreciated that FIG. 11 describes software that acts as anintermediary between users and the basic computer resources described inthe suitable operating environment 1100. Such software includes anoperating system 1128. Operating system 1128, which can be stored ondisk storage 1124, acts to control and allocate resources of thecomputer system 1112. System applications 1130 take advantage of themanagement of resources by operating system 1128 through program modules1132 and program data 1134 stored either in system memory 1116 or ondisk storage 1124. It is to be appreciated that the claimed subjectmatter can be implemented with various operating systems or combinationsof operating systems.

A user enters commands or information into the computer 1112 throughinput device(s) 1136. Input devices 1136 include, but are not limitedto, a pointing device such as a mouse, trackball, stylus, touch pad,keyboard, microphone, joystick, game pad, satellite dish, scanner, TVtuner card, digital camera, digital video camera, web camera, and thelike. These and other input devices connect to the processing unit 1114through the system bus 1118 via interface port(s) 1138. Interfaceport(s) 1138 include, for example, a serial port, a parallel port, agame port, and a universal serial bus (USB). Output device(s) 1140 usesome of the same type of ports as input device(s) 1136. Thus, forexample, a USB port may be used to provide input to computer 1112, andto output information from computer 1112 to an output device 1140.Output adapter 1142 is provided to illustrate that there are some outputdevices 1140 like monitors, speakers, and printers, among other outputdevices 1140, which require special adapters. The output adapters 1142include, by way of illustration and not limitation, video and soundcards that provide a means of connection between the output device 1140and the system bus 1118. It should be noted that other devices and/orsystems of devices provide both input and output capabilities such asremote computer(s) 1144.

Computer 1112 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1144. The remote computer(s) 1144 can be a personal computer, a server,a router, a network PC, a workstation, a microprocessor based appliance,a peer device or other common network node and the like, and typicallyincludes many or all of the elements described relative to computer1112. For purposes of brevity, only a memory storage device 1146 isillustrated with remote computer(s) 1144. Remote computer(s) 1144 islogically connected to computer 1112 through a network interface 1148and then physically connected via communication connection 1150. Networkinterface 1148 encompasses wire and/or wireless communication networkssuch as local-area networks (LAN) and wide-area networks (WAN). LANtechnologies include Fiber Distributed Data Interface (FDDI), CopperDistributed Data Interface (CDDI), Ethernet, Token Ring and the like.WAN technologies include, but are not limited to, point-to-point links,circuit switching networks like Integrated Services Digital Networks(ISDN) and variations thereon, packet switching networks, and DigitalSubscriber Lines (DSL).

Communication connection(s) 1150 refers to the hardware/softwareemployed to connect the network interface 1148 to the bus 1118. Whilecommunication connection 1150 is shown for illustrative clarity insidecomputer 1112, it can also be external to computer 1112. Thehardware/software necessary for connection to the network interface 1148includes, for exemplary purposes only, internal and externaltechnologies such as, modems including regular telephone grade modems,cable modems and DSL modems, ISDN adapters, and Ethernet cards.

What has been described above includes examples of the subjectinnovation. It is, of course, not possible to describe every conceivablecombination of components or methodologies for purposes of describingthe claimed subject matter, but one of ordinary skill in the art mayrecognize that many further combinations and permutations of the subjectinnovation are possible. Accordingly, the claimed subject matter isintended to embrace all such alterations, modifications, and variationsthat fall within the spirit and scope of the appended claims.

In particular and in regard to the various functions performed by theabove described components, devices, circuits, systems and the like, theterms (including a reference to a “means”) used to describe suchcomponents are intended to correspond, unless otherwise indicated, toany component which performs the specified function of the describedcomponent (e.g., a functional equivalent), even though not structurallyequivalent to the disclosed structure, which performs the function inthe herein illustrated exemplary aspects of the claimed subject matter.In this regard, it will also be recognized that the innovation includesa system as well as a computer-readable medium havingcomputer-executable instructions for performing the acts and/or eventsof the various methods of the claimed subject matter.

In addition, while a particular feature of the subject innovation mayhave been disclosed with respect to only one of several implementations,such feature may be combined with one or more other features of theother implementations as may be desired and advantageous for any givenor particular application. Furthermore, to the extent that the terms“includes,” and “including” and variants thereof are used in either thedetailed description or the claims, these terms are intended to beinclusive in a manner similar to the term “comprising.”

1. A system for online changing a routine executed by a controller tosequence actions performed by a process, the system comprising: anonline editor responsive to changes to a language element of a routinecurrently executed by a controller to save a pending edit of thelanguage element; and a change monitor responsive to the online editorto identify a change between an original language element and thepending edit to perform a measure preventing reset of the routine. 2.The system of claim 1, wherein the change monitor performs the measurepreventing the reset of the routine comprising sending a warning of areset prior to acceptance of the pending edits.
 3. The system of claim2, wherein the change monitor causes a reset symbol to be depicted on agraphical user interface.
 4. The system of claim 3, wherein graphicaluser interface responds to selection of the reset symbol by navigatingto a depiction of the pending edit.
 5. The system of claim 3, whereinthe graphical user interface responds to the change monitor by depictinga selected one of a group consisting of a reset warning icon depicted ona status bar, a reset warning tool tip activated by a cursor, and areset warning popup window.
 6. The system of claim 1, wherein the changemonitor detects change notifications from another online editor incommunication with the first online editor, and prevents a warning inresponse to detecting that a change notification from the other onlineeditor that would not cause an additional basis for a reset.
 7. Thesystem of claim 1, wherein the routine is a sequential function chartand the change monitor performs a sequential function chart specificcomparison to identify whether a change in a language elementnecessitates reset of the routine to implement.
 8. The system of claim7, wherein the sequential function chart specific comparison comprisesdetermining whether the change pertains to (1) Is Initial Step attributeor (2) What Is the Next Transition attributes of a Step languageelement.
 9. The system of claim 7, wherein the sequential function chartspecific comparison comprises determining whether the change pertains to(1) What is the next Action, (2) What is the parent Step, (3) What isthe Action qualifier, and (4) is the Action Boolean attributes of anAction language element.
 10. The system of claim 7, wherein thesequential function chart specific comparison comprises determiningwhether the change pertains to What is the Next Element attribute of aTransition language element.
 11. The system of claim 7, wherein thepending change pertains to an element deletion, the change monitorresponsive to a deletion of a language element contained in an originalversion of the routine to perform the measure preventing the reset ofthe routine.
 12. The system of claim 1, wherein the change monitorfurther comprises a reset list tracking an original language component,a pending edits language component, and a test language component.
 13. Amethod of performing online editing of a current routine executed by acontroller to sequence operations of a process, comprising: classifyingchanges of language elements usable to form a routine as requiring ornot requiring a reset of a controller to implement; monitoring pendingedits to an online routine; and identifying a change of a languageelement as requiring a reset and performing a measure to prevent reset.14. The method of claim 13, further comprising performing the measure toprevent reset by sending a warning of a reset prior to acceptance of thepending edits.
 15. The method of claim 13, further comprising performingthe measure to prevent reset by depicting a reset symbol on a graphicaluser interface.
 16. The method of claim 15, further comprisingresponding to selection of the reset symbol by navigating to a depictionof the pending edit.
 17. The method of claim 15, further comprisingperforming the measure to prevent reset by depicting a selected one of agroup consisting of a reset warning icon depicted on a status bar, areset warning tool tip activated by a cursor, and a reset warning popupwindow.
 18. The method of claim 13, further comprising: detecting changenotifications from another online editor in communication with a firstonline editor; and preventing a reset warning from being depicted inresponse to detecting that a change that would not cause a reset. 19.The method of claim 1, wherein the routine is a sequential functionchart.
 20. The method of claim 19, further comprising comparing specificattributes of a sequential function chart to identify whether change ina language element necessitates reset of the controller to commit. 21.The method of claim 20, further comprising: in response to determiningthe language element is a Step, determining whether the change pertainsto (1) Is Initial Step attribute or (2) What Is the Next Transitionattributes; in response to determining the language element is anAction, determining whether the change pertains to (1) What is the nextAction, (2) What is the parent Step, (3) What is the Action qualifier,and (4) is the Action Boolean attributes; and in response to determiningthe language element is a Transition, determining whether the changepertains to What is the Next Element attribute of a Transition languageelement.
 22. The method of claim 13, further comprising responding to adeletion of a language element contained in an original version of theroutine by performing the measure preventing the reset of thecontroller.
 23. The method of claim 13, further comprising tracking anoriginal language component, a pending edits language component, and atest language component.
 24. The method of claim 13, further comprisingclassifying changes of a language element as a selected one of an addedlanguage element, a modified language element, and a deleted languageelement.
 25. A system for online changing a routine executed by acontroller to sequence actions performed by a process, comprising: meansfor classifying changes of language elements usable to form a routine asrequiring or not requiring a reset of a routine to commit; means formonitoring pending edits to an online routine; and means for identifyinga change of a language element as requiring a reset and performing ameasure to prevent reset.